If you are migrating SAS Marketing Optimization 5.1 to SAS Marketing Optimization 5.3, you might experience a failure when running the SAS Migration Utility. This problem occurs if you have previously customized either the SAS Application Server Context autoexec file (appserver_autoexec.sas) or the SAS Marketing Optimization autoexec file (MarketingOptimization_autoexec.sas).

Note that in later versions of the SAS Migration Utility, executing the Application Server Context autoexec file is eliminated, but executing the SAS Marketing Optimization 5.1 autoexec file remains.

If these customizations to the SAS^® autoexec files have execution dependencies on SAS options, environment variables, or path settings, and these dependencies are established outside of the autoexec files, the SAS Marketing Optimization SAS Migration Utility extension might fail.

For example, you have updated the sasv9.cfg file in the Application Server Context directory, such as SAS-Configuration-Directory/Lev1/SASMain, to include a -insert sasautos custom-path statement. You have updated the autoexec file to invoke a macro located in the custom-path directory. If this occurs, you will see the following in the SAS Migration Utility migrate.log in the output directory:

2009-10-15 11:37:16,747 [ERROR ] Target mktopt.FullAnalyze threw Exception The
batch SAS execution process failed.
C:\DOCUME~1\TEMP\LOCALS~1\Temp\3\pft88.tmp\Extensions\mktopt\mktopt.xml:413: The
batch SAS execution process failed.
At com.sas.apps.migration.mktopt.taskdefs.MktoptAnalysisTask.executeSascmd(MktoptAn
alysisTask.java:524) and you will see an error similar to the following one in the
analyze_metadata_versioncheck.log in the mktopt/analysisResults directory:

NOTE: AUTOEXEC source line.
35         %stp_initialize_vars;
        
WARNING: Apparent invocation of macro STP_INITIALIZE_VARS not resolved.


ERROR 180-322: Statement is not valid or it is used out of proper order.

Note that the macro stp_initialize_vars above is an example for illustrative purposes. The error that you will see would include the name of your custom macro (if that is the reason for the execution failure).

The workaround is to provide versions of these autoexec files to the SAS tier SAS Marketing Optimization SAS Migration Utility extensions that do not contain such customizations.

Perform the following steps for each customized autoexec file:

1. Locate the autoexec file.
1. Unless you have renamed or relocated it, the Application Server Context autoexec file is typically located at SAS-configuration-directory/Lev1/SASMain/appserver_autoexec.sas.
2. Unless you have renamed or relocated it, the SAS Marketing Optimization 5.1 autoexec file is typically located at SAS-configuration-directory/Lev1/SASMain/MarketingOptimization_autoexec.sas.
2. Copy the customized autoexec file to a new file (with a name of your choosing).
3. Edit the copied file and remove your customizations. It is sufficient to just comment out the customizations.
4. Depending on which autoexec files you needed to change, add the following property or properties to the SAS server tier smu.properties file as the next-to-last property in the file:
1. mktopt.appserver.autoexec.directory.and.name=fully-qualified-name-of-copy-of-Application-Server-Context-autoexec-file.
2. mktopt.autoexec.directory.and.name=fully-qualified-name-of-copy-of-SAS-Marketing-Optimization-autoexec-file.

   These properties are described in Appendix 2 of the SAS Intelligence Platform: 9.1.3 to 9.2 Migration Guide document.

5. Rerun the SAS Migration Utility.

Special Note: Other products, such as SAS^® Web Analytics, might have the exact customization to the sasv9.cfg file that is described above. So even if you have not made any customizations to the autoexec files, certain products might already have such customizations, and these must be removed in copies of the autoexec files that are provided to the SAS tier SAS Marketing Optimization SAS Migration Utility extension.

Operating System and Release Information